Protege X Record Hierarchy

To prevent duplication of system events and ensure correct status reporting, events and status updates must only be received from a single controller. To achieve this, Protege X assigns a host controller to resources which generate event and status information.

Host controller operation is relevant to areas, doors, elevators and input types. These 'hostable' record types will now be downloaded to only a single controller - their host controller - and manual controls will only be sent to the controllers that host these records.

If no host controller is assigned, areas, doors and elevators are not downloaded to any controller. Manual controls will not be sent. Input types are downloaded to all controllers, until a host controller is established.

A host controller is assigned to a hostable record based on the relationships of associated controller-specific records. Any time a record with a controller relationship is selected in the programming of a hostable record, the controller in that relationship automatically becomes the host controller for the hostable record.

• When no controller-specific records are assigned to the hostable record it has no host controller. When selecting records such as inputs and outputs you will be able to specify any controller in the same location as the hostable record and select records associated with that controller.
  • When selecting records that are programmed under a controller, such as inputs/outputs and expanders, the parent controller of the selected record is assigned as the host controller.
  • When selecting records that have a host controller assigned, such as doors and areas, the host controller of the selected record is assigned as the host controller.
  • When selecting record groups, such as output groups and door groups, the controller associated with that group is assigned as the host controller, only if all records in the group have the same relationship. If any of the records in the group have a relationship with a different controller, or no controller relationship, the selection is ignored and no host controller is assigned based on this association.
• Once a host controller is associated with a hostable record, selection lists are filtered so that only records programmed under the host controller can be viewed and selected when assigning records to the hosted record. You will not be able to see or select records programmed under other controllers.
• When new hostable records are added, if there is only one controller in the location it will automatically be assigned as the host controller for those new records.
• When a new controller is created all hostable records which are auto-generated as a result of the downstream record creation process will automatically have that controller assigned as their host controller.
• When a controller database is imported all imported hostable records will automatically have that controller assigned as their host controller.
• Once a host controller is associated with a hostable record this cannot be changed.

The host controller for each hosted record is displayed in the Controller column on the relevant resource type page, and in the Related objects list of each hosted record. For hostable records with no host controller assigned, the Controller listing will be displayed as 'Unassigned'.

Once a host controller is assigned to a record it is not possible to change the host controller. The only option is to remove this record and add a new one with the required configuration.

Location-Level Record Selection

When selecting location-dependent records (areas, doors, elevators, floors, controllers and their downstream records), only records from the same location can be selected. Protege X does not support cross-location operation, so records and devices are only able to operate within their programmed location.

Once a host controller is established you can only select records which are programmed under the host controller.

The following table identifies the programming hierarchy and relationships for each resource type.

Place	Location	Controller
Operators	Areas	Inputs
Roles	Doors	Outputs
Users	Elevators	Trouble inputs
Access levels	Floors	Input expanders
Schedules	Controllers	Output expanders
Daylight savings		Analog expanders
Phone numbers		Reader expanders
Input types*		Keypads
Door types		Smart readers
Credential types		Automations
Door groups		Programmable functions
Area groups		Services
Menu groups
Output groups
Keypad groups
Holiday groups
Elevator groups
Floor groups
Location groups
Personal access tokens
Locations

*Input types are downloaded to all controllers until a host controller is assigned based on records such as outputs and areas assigned to that input type. Then they are downloaded only to the host controller.